Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#108499 - 30/07/2002 20:11 [option] notify=1 (Empeg Web Interface woes)
RobRoy
stranger

Registered: 17/06/2002
Posts: 39
I am having trouble getting the web interface to work correctly.

I have loaded up the latest build (beta 13), latest hijack (289) and have downloaded and installed the latest update to the web interface.

I have poured over the FAQ, and have made the necessary registry entry to allow me to edit the config.ini from within emplode.

First of all, I can't find an [output] section anywhere. Should it be there, or is it a new entry?

Secondly, when I add it to either the very beginning or end of the config.ini file, it doesn't seem to have any effect. I still get the error from the web interface that tells me I need to add that line to the config.ini.

I have performed a sync after making the change, and I have also tried a refresh of the web page. Still doesn't work.

I realize I am probably missing something quite simple, I just can't see it right now.

Please advise!

TIA,

Rob


Top
#108500 - 30/07/2002 20:21 Re: [option] notify=1 (Empeg Web Interface woes) [Re: RobRoy]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31602
Loc: Seattle, WA
The player needs to be fully rebooted in order for it to re-read the changes you made to config.ini. Synching is not enough, it needs to be a hard reboot.
_________________________
Tony Fabris

Top
#108501 - 30/07/2002 20:22 Re: [option] notify=1 (Empeg Web Interface woes) [Re: tfabris]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31602
Loc: Seattle, WA
I think I'll add that to the FAQ now.
_________________________
Tony Fabris

Top
#108502 - 31/07/2002 07:18 Re: [option] notify=1 (Empeg Web Interface woes) [Re: tfabris]
Dava
member

Registered: 06/12/2000
Posts: 192
Loc: Bucks UK
I have had this problem also. I forgot about it until now but I have [output] notify=1 as the first 2 lines in the config and it still doesn't work.

Any other ideas?
_________________________
MK2 smoked 32Gb S/n 090000949 MK2a Blue 20GB racked and out of sync

Top
#108503 - 31/07/2002 07:26 Re: [option] notify=1 (Empeg Web Interface woes) [Re: tfabris]
Dava
member

Registered: 06/12/2000
Posts: 192
Loc: Bucks UK
Sussed it...

I also added:
[serial]
car_rate=115200
notify=1

...and it works fine.

So you may want to add to the FAQ that you need to have serial notify on for it to work.
_________________________
MK2 smoked 32Gb S/n 090000949 MK2a Blue 20GB racked and out of sync

Top
#108504 - 31/07/2002 07:30 Re: [option] notify=1 (Empeg Web Interface woes) [Re: Dava]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 14496
Loc: Canada
Not true.

All that I have is this, at the very top of config.ini:
[output]

notify=1
Works fine.

Just make you you disconnect/reconnect POWER after saving the new config.ini -- a simple "restart" won't (always) do it.

-ml


Edited by mlord (31/07/2002 07:31)

Top
#108505 - 31/07/2002 07:58 Re: [option] notify=1 (Empeg Web Interface woes) [Re: mlord]
Dava
member

Registered: 06/12/2000
Posts: 192
Loc: Bucks UK
That is indeed a most wierd thing.

I have played some more and it appears to be the car_rate setting which causes it to work or not. If I take out the car_rate setting it stops working. Put it back and the FID is there in vital signs.

Can someone see if theirs does the same.

Here is the start of the config I use.

[output]
notify=1
[serial]
car_rate=115200
[tuner]
region=europe
[controls]
stalk_side=none
[Options]
Name=Silver 32
_________________________
MK2 smoked 32Gb S/n 090000949 MK2a Blue 20GB racked and out of sync

Top
#108506 - 31/07/2002 09:17 Re: [option] notify=1 (Empeg Web Interface woes) [Re: Dava]
charcoalgray99
enthusiast

Registered: 14/05/2001
Posts: 279
I asked loren to add this to the FAQ a while ago, I had the same problem...

Allows access to /proc/empeg_notify on the player, which is created by the Hijack kernel. The data shown in /proc includes track name/fid/position/artist/album/etc.. the same is dumped to the serial port by notify=1. Also allows for initial sequences of button presses to be run as soon as the player starts up with "Initial=xxxxx" lines in IR_Translate. Also shows FID in Vital Signs screen. If you're trying to get serial output when docked in the sled, make sure you also have [serial]car_rate=115200 in your config.ini

Tom

Top
#108507 - 31/07/2002 10:09 Re: [option] notify=1 (Empeg Web Interface woes) [Re: charcoalgray99]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31602
Loc: Seattle, WA
But I just added the [output] notify=1 to a friend's player and it worked fine without the car_rate=115200 command. I checked it.
_________________________
Tony Fabris

Top
#108508 - 31/07/2002 10:10 Re: [option] notify=1 (Empeg Web Interface woes) [Re: tfabris]
charcoalgray99
enthusiast

Registered: 14/05/2001
Posts: 279
Was it docked in a sled and working without car_rate=115200 ?

Tom

Top
#108509 - 31/07/2002 10:24 Re: [option] notify=1 (Empeg Web Interface woes) [Re: charcoalgray99]
Dava
member

Registered: 06/12/2000
Posts: 192
Loc: Bucks UK
Good call I think.

This is when it is over the wireless in the car sled.

My unit at home on AC does not have car_rate and works fine.
_________________________
MK2 smoked 32Gb S/n 090000949 MK2a Blue 20GB racked and out of sync

Top
#108510 - 31/07/2002 10:42 Re: [option] notify=1 (Empeg Web Interface woes) [Re: charcoalgray99]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31602
Loc: Seattle, WA
Was it docked in a sled and working without car_rate=115200 ?

It was in my office docking station. Do you think that has something to do with it?
_________________________
Tony Fabris

Top
#108511 - 31/07/2002 10:53 Re: [option] notify=1 (Empeg Web Interface woes) [Re: tfabris]
charcoalgray99
enthusiast

Registered: 14/05/2001
Posts: 279
Well I'm confused now... I just removed it and it's working in my home docking station.

Tom

Top
#108512 - 31/07/2002 11:06 Re: [option] notify=1 (Empeg Web Interface woes) [Re: Dava]
foxtrot_xray
addict

Registered: 03/03/2002
Posts: 687
Loc: Atlanta, Georgia

In reply to:


I forgot about it until now but I have [output] notify=1 as the first 2 lines in the config and it still doesn't work.




Hmm.. I just installed the web interface, and added the two lines ([output] and notify=1) to the *END* on my config.ini, and did not have a hitch at all.

Maybe there's a bug somewhere (misplaced 'if) where if it appears before a different section it gets ignored?

Me.
_________________________
Mike 'Fox' Morrey 128BPM@124MPH. Love it! 2002 BRG Mini Cooper

Top
#108513 - 31/07/2002 11:15 Re: [option] notify=1 (Empeg Web Interface woes) [Re: charcoalgray99]
charcoalgray99
enthusiast

Registered: 14/05/2001
Posts: 279
Nevermind, I figured it out.

[serial] car_rate=115200 is only required if you are in a docking station and NOT using a dummy ac plug.

Tom

Top
#108514 - 31/07/2002 11:29 Re: [option] notify=1 (Empeg Web Interface woes) [Re: charcoalgray99]
tfabris
carpal tunnel

Registered: 20/12/1999
Posts: 31602
Loc: Seattle, WA
Let me get this straight...

So there is only a problem if the player thinks it's in "car" mode and you're trying to make use of the notify=1 data?
_________________________
Tony Fabris

Top
#108515 - 31/07/2002 12:41 Re: [option] notify=1 (Empeg Web Interface woes) [Re: tfabris]
charcoalgray99
enthusiast

Registered: 14/05/2001
Posts: 279
Correct.

Tom

Top
#108516 - 01/08/2002 00:04 Re: [option] notify=1 (Empeg Web Interface woes) [Re: charcoalgray99]
Derek
addict

Registered: 16/08/1999
Posts: 453
Loc: NRW, Germany
Aren't the http and ftp servers turned off in car mode unless you specifically askr for them to be turned on in the config.ini to leave more memory for caching? From the FAQ: dc_servers=1 Allows kftpd/khttpd to run in DC/Car mode, which is off by default otherwise. No idea why the serial speed should have and effect.
_________________________
(list 6284, Mk1 S/N 00299 4GB blue [sold]. Mk2 S/N 080000094 20GB blue)

Top
#108517 - 01/08/2002 02:02 Re: [option] notify=1 (Empeg Web Interface woes) [Re: Derek]
Dava
member

Registered: 06/12/2000
Posts: 192
Loc: Bucks UK
I think Tom has it pegged.

It is not the DC servers issue or I would get no data at all when in the car. The web interface shows fine apart from the now playing data. It was the same in Vital Signs, no FID displayed.

Adding Car_rate fixed my problem although only Mark probably knows why.
_________________________
MK2 smoked 32Gb S/n 090000949 MK2a Blue 20GB racked and out of sync

Top